home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
scht_407.zip
/
SCHT!407.DOC
< prev
next >
Wrap
Text File
|
1991-11-10
|
31KB
|
946 lines
┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌──┬──┐ ┌─────┐ ┌─────┐ ┌─┐
░│ ───┤░│ │ │░│ ── │░│ ── │░│ ───┤░░│ │░│ │ │░│ │ │░└─┐ ┌─┘░░│ │░
░│ │░│ │░│ ── │░│ ─┤░│ ───┤░░│ ───┤░│ │░│ │░░░│ │░░░░│ │░
░├─── │░│ │ │░│ │░│ │░│ │░░│ │░│ │░│ │ │░░░│ │░░░░└─┘░
░│ │░│ │ │░│ │░│ │ │░│ │░░│ │░│ │ │░│ │ │░░░│ │░░░░┌─┐░
└─────┘ └──┴──┘ └─────┘ └───┴─┘ └─────┘ └─────┘ └──┴──┘ └──┴──┘ └─┘ └─┘
V e r s i o n 4 . 0 7
C o p y r i g h t ( C ) 1 9 9 1 S h a w n G r e s h a m
From
Joel Karr's
E l e c t r o d e s B B S
903-868-2794 FIDOnet 1/19:55
C r e d i t s
─────────────
The following products are copyrighted material and/or
trademarks of their copyright and/or trademark holders
respectively:
DESQview Quarterdeck Systems
Remote Access, RABBS Continental Software
MASM Microsoft Corporation
TASM Borland International
Their names are used only for reference to aide in
installation and usage of SabreChat!.
W h a t i s S a b r e C h a t !
───────────────────────────────────
SabreChat! is a cross-node/cross-environment chat
utility for Remote Access Bulletin Boards Systems
providing a means for users on different nodes to conduct
'real-time' communication.
SabreChat! provides the following options:
■ Character-by-character communications instead of
the confusing, jerky line-by-line method.
■ Runs on nodes separated by DESQview, Networks supporting
NetBios, Novell Netware, or WINDOWS graphic environment.
■ Supports remote ANSI on/off (hi/lo intensity), Avatar and
40/80 column displays.
■ Local screen can be updated with an optional direct screen
write mode with an CGA Snow Removal option for faster text
display as well as a BIOS update mode and the traditional
text output method. Supports DESQview's direct screen write
buffer.
■ Supports up to 49 nodes!
■ Allows paging to a user on another RA node.
■ Optional two modes of name-prompting to reduce confusion in
conversations of 3 or more users that can be changed by the
user to fit his or her desires.
■ Can be used to create Conference menus for more than
one concurrent chat session under a network or multitasker.
NOTICE:
The unregistered version of SabreChat! has a ten-minute
time restriction. A user may re-enter SabreChat! as
often as he wishes though.
SabreChat! is written in 8088 assembly language and assembled
with the Turbo Assembler Version 2.00 for smaller EXE size and
faster execution.
R e q u i r e m e n t s
───────────────────────
SabreChat! requires the following to operate correctly.
■ A Communication Fossil. Examples : BNU and X00
■ ANSI.SYS if you use the S3 (use ASCII/ANSI Text Output
function explained later).
■ Only needs about 25k to operate.
■ A multitasker, or a novell or netbios network.
NOTE: As of version 4.07, SabreChat! will no longer
support Remote Access Version 1.01 or earlier.
Earlier versions of SabreChat! should be retained
to allow usage with earlier version of RA.
L i c e n s i n g A g r e m e n t
───────────────────────────────────
■ You may use SabreChat! for a period of four weeks to determine
it's usefulness on your system. After this period you MUST
register SabreChat! or discontinue the use of it.
■ You are encouraged to distribute SabreChat! provided no fee is
charged for distribution, the distribution archive is NOT to
be modified.
■ Registration will entitle you to future versions of SabreChat!
but subject to any special condition of that release.
■ Sabre Products or Shawn Gresham is not obligated to provide
future versions, or support, for SabreChat!.
■ You may not modify or reverse-engineer SabreChat!.
■ SabreChat! may NOT be included for distribution as part of any
software library that is sold for profit.
■ Sabre Products, or Shawn Gresham's, liability is limited to
the amount paid for registration only.
R e g i s t r a t i o n
───────────────────────
Welcome to revision 4.07!!!
Revision 4.07.00 will, unfortunatetly, be the first version of
SabreChat! to have true registrations.
The following infomation is needed for registration:
Sysop name
System name
Primary BBS phone number
Postal address
FidoNet address (if available)
Please send $15 US for registration, along with the above
information, to one of the following locations:
USA:
"Registration Schat!"
C/- Shawn Gresham
Route 1 Box 544
Gordonville, TX 76245
USA
"Registration Schat!"
C/- Joel Karr
Route 1 Box 281c
Sherman, TX 75090
USA
AUSTRALIA:
"Registration Schat!"
C/- Terry Harvey
PO Box 593
Burwood NSW 2134
AUSTRALIA
Accepts VISACARD,
MasterCard, BankCard
■ You MUST include all the registration information correct for
proper key generation.
■ Checks or money orders should be made payable to the person of
the registration site.
■ Include either a stamped, self-addressed envelope, or a FidoNet
address for a receipt of your payment.
R e g i s t r a t i o n K e y
───────────────────────────────
Upon registering you will receive your personal key via netmail
(if availble). If netmail is not available to you, then after
receiving your payment receipt via. return mail, call the
registration locations' BBS and a PERSONAL message with the key
file will be attached on hold for you. Each key is a small file
(120 bytes) in size which contains information about your
registration. Place a copy in your system directory that the SET
SCHAT!= points to (normaly your RA system directory).
SabreChat! detects a valid key upon execution and switches into
registered mode. Registration information is displayed at program
execution, and the "please register" is removed. This removes the
10 min restriction of non registered mode.
WARNING! DO NOT make your key available to anyone! Doing so will
violate your registration agreement with Sabre Products.
S C h a t ! F i l e s
───────────────────────
The following files are included in the SabreChat! archive
file.
SCHAT!.EXE The main executing file.
SCHT!407.DOC This Manual.
SETSCHT.COM The file allows you to set the defaults that
SabreChat! will use on the command line.
SCHAT!.TXT A sample text file that will display to each
user as he enters SabreChat!.
MXR!.COM Creates a memory buffer for SabreChat! when
being used under a multitasker. Now supports
up to 49 nodes at once. This program is the
descendent of MIXER!.COM that was with version
2.05 and before and is not compatible with
the older version of SabreChat! nor is 4.07
compatible with the old MIXER!.COM.
NETMXR!.COM This allows simultaneous execution of
several nodes of SabreChat! under a
multi-tasker on several machines on a
network. (yeah, neat trick)
REMOVE!.COM Removes MXR!.COM and NETMXR!.COM from memory.
MXR!.DOC Help on Mixer!
Files created by SabreChat! during execution:
SCHAT!.SAV The default file. Created by SETSCHT.COM.
SCHAT!.CNF Conference Information.
SCHAT!.USR User Information.
I n s t a l l i n g S a b r e C h a t !
─────────────────────────────────────────
To install SabreChat!, you will need to create a environment
variable called SCHAT! and point it toward the main directory
of your bulletin board system. For Remote Access systems,
SCHAT! will be set to the same directory as your RA variable
is set. This directory must be accessable by all nodes.
For example: SET SCHAT!=C:\RA
The semaphore path can be set with the SabreChat! utility
SETSCHT.COM. SabreChat! will then look for the NODE?.RA
files in the semaphore path.
Through experience, we have discovered that it is benificial
to delete the files: SCHAT!.CNF and SCHAT!.USR in your
AUTOEXEC.BAT file. SabreChat! will re-create them when
executed and this will prevent any garbage from being left
over from a lock-up.
Also if you create or modify the SCHAT!.TXT file that came
with SabreChat!, you can give additional information to
users entering SChat!. The text file could be used for
anything you wish: newsletters, warnings, greetings,
additional help, and coupled with a random file creator you
could use the file for random quotes or such. Please do not
include any control characters into the text file other than
carriage return and linefeed.
I would suggest that you thoroughly read this document for the
information that you will need for your system.
For help with MXR!.COM please read MXR!.DOC included in the
SabreChat! package.
U p d a t i n g S a b r e C h a t !
─────────────────────────────────────
If you already have SabreChat! and are upgrading to a newer
version please do the following things to make the upgrade
as painless as possible.
1. Delete the files SCHAT!.USR and SCHAT!.CNF.
2. If the new version of SChat! has a different
sized SCHAT!.SAV delete that too and re-run
SETSCHT to reconfigure SabreChat!.
C o m m a n d L i n e O p t i o n s
───────────────────────────────────────
Below is a listing of all the command line parameters needed to
execute SabreChat!. I have included a full length description
of each and usage examples to help prevent confusion.
A ASCII/ANSI/Avatar Usage.
This flag determines whether ASCII, ANSI, or Avatar commands
are sent to an online user.
A<0, 1, 2, or 3> where 0 = None,
1 = Ansi,
2 = Avatar,
3 = Ansi/Avatar.
Default: A0 - None
Example: SCHAT! A3 - Ansi/Avatar Mode
B Set Immediate Users Baudrate.
This command sets the baud rate for an immediate user
on whatever communications port that was specified with
the P <set port number> option. Please see the following
chapter over IMMEDIATE USERS.
B<baud> where baud is a rate 300 to 38400.
Default: Leaves the port at whatever setting it was at.
Example: SCHAT! &Gina_Lewter B1200 P0
-- Handles Online User at 1200 baud
on port 0.
C Select Talk Port.
Selects communications port to be used for cross-node
communications. Not to be confused with P (Call Com
Port) that determines the communication port for the
caller. Only use this command if you wish to use a
communications port for cross-node chatting otherwise
do not include it on the command line.
C<port> where port is a valid communications port 1-8.
Default: None
Example: SCHAT! C2 - Use COM2
D NetBios Double Checking Mode. (NETBIOS and NOVELL ONLY)
This command enables SabreChat!'s character double
check mode. Netbios has a tendency to lose characters
on systems with 4 or more nodes due to the fact of
netbios communication when the network drives are being
heavily used. By using the D command line parameter, Sabre
Chat! will try to double check each character sent to help
cut down on the character loss.
NOTE: I would recommend that you only use this command,
if you are indeed experiencing character loss problems
on a multiserver system or a system where the server
is a node of the bbs.
Default: Disabled
Example: SCHAT! D - enable netbios double checking
F Define Message Filename.
RA versions 1.10 and above use NODE?.RA to send
messages to other nodes. The F command allows the sysop
to specify the filename if he does not wish to use
NODE?.RA.
F<filename> where filename is a legal filename
with ? in place of the node
number.
Default: FNODE?.RA
Example: SCHAT! FONLINE?.MSG
H Use Handle/Aliases.
When this flag is set SabreChat! will use caller's
handles/aliases instead of their names.
H<0 or 1> where 0 = use names, and 1 = use handles.
Default: H0
Example: SCHAT! H1 -- use handles
I Use Novell Netware IPX DataGram Routines. (NOVELL ONLY)
Allows SabreChat! to run on Novell Netware systems that
have loaded IPX without need of a clumsy netbios shell.
Default: Off
Example: SCHAT! I - use Novell Netware Routines.
L Use NetBios and Specify LANA Card Number. (NETBIOS ONLY)
Allows SabreChat! to run on systems running NetBios
without having to use an RS232 cable. Do not include if
you wish to use the C <talk port> or V<Memory Buffers>
options.
L<LANA Card> where LANA Card is 0 or greater.
Default: None
Example: SCHAT! L0 - activates netbios with LANA 1
M Set Name Prompting Default.
This parameter sets the prompting type that will be
default when a user enters SabreChat!. The user can
later change his prompting by use of the ^T toggle
prompting mode command, if he or she prefers another
mode.
M<0,1,or 2> where 0 is NONE (disabled)
1 is First Name
example: --Shawn--
hiya
2 is initial mode
example: SG> hiya
Default: M0 - Disabled
Example: SCHAT! M1 - First Name prompting enabled
N Assign Node.
Selects node to use when reading USERON.BBS for the user
information.
N<node> where node is a valid RA node 1-49.
Default: N1 - Node 1
Example: SCHAT! N3 - Node 3
O Select Conference Name.
Now with version 4.07 of SabreChat!, multitasking
systems can now take advantage of the conferencing
ability before only available to networks. This
command line option allows the SysOp
to specify the initial conference that the user will be
involved in upon entering SabreChat!. More Information
on conferencing is included later in the 'Conferencing'
chapter in this manual.
O<conference name> where conference name is a
valid conference name.
Default: OSCHAT!
Example: SCHAT! L0 OGIRLS - use netbios with the
name GIRLS.
P Select Caller Communications Port.
Specifies the com port to be used for the online caller.
Be careful not to confuse this command with the C <talk
port> option. This option is ignored if the caller is
local (i.e. baudrate 0). Should be the same port as
being used by the bulletin board.
P<port> where port is a valid communications port 1-8.
Default: None (local)
Example: SCHAT! P1 - Use COM1
S Display Mode.
Sets the local screen update mode. Modes available are
Direct Screen Update (the fastest), Direct Screen Update
with CGA Snow Removal, Bios Output Routines (slightly
slower than direct) and normal ASCII/ANSI text prints
(the slowest). The Direct Screen Update and BIOS modes
should auto-adapt to your video environment (i.e. 80x25,
80x43, 80x50, etc...) and place the status bar at the
bottom. If you have problems with the direct display,
try downgrading to BIOS and even to the text output
routine if all else fails and SChat! will operate as it
did in the earlier versions. The status bar is not
available in the text output mode.
S<0, 1, 2, or 3> where 0 is direct
1 is direct with CGA Snow Removal
2 is Bios Output
3 is ASCII/ANSI text output
Default: S0 Direct
Example: SCHAT! S2 - Use Bios
T Set Minutes Remaining.
Sets the maximum amount of time allowed in chat in
minutes before SabreChat! will return the user to the
BBS.
NOTICE:
This command is ALWAYS set to 10
T<minutes> where minutes is 0-255.
Default: T20 - 20 minutes
Example: T90 - 1 Hr 30 Minutes
U Ask User for Initial Conference Names.
This option causes SabreChat! to prompt the user for a
conference name upon entering.
Default: None
Example: SCHAT! U
V Use Memory Buffers. (MULTITASKER and NETMXR! ONLY)
Allows SabreChat! to communicate across windows on a
multitasking system. This option requires that MXR!.COM
or NETMXR!.COM was executed before entering the
multitasker. Please read the 'Mixing Systems' chapter
later in this manual if you wish to operate under a
multitasker and a network at the same time.
Default: None
Example: SCHAT! V - allows operation under a multitasker.
Z Set Screen Length.
Sets the screen length in lines for the direct and BIOS
output modes. Does not effect the text output routines
or the output to an online user. The function is
included in case auto-detection (default) fails to
correctly estimate the video mode. Also useful for
setting smaller number of lines in DESQview so that the
SChat! status bar will be visible in the DESQview
window.
Default: Detect
Example: SCHAT! Z10 - sets number of lines to 10.
- Set User Inactivity Timeout Time.
This command line parameter allows the sysop to set the
time in which SabreChat! will abort if the user is
inactive. A warning will be sent to the user one minute
before SabreChat! aborts back to the system.
-<2-255> where 2-255 is the minutes before abort.
Default: -5
Example: SCHAT! -3 - sets limit to 3 minutes.
& Local Non-BBS Operation Mode.
This option allows the sysop enter SabreChat! as a
different node, but without need of an actual BBS node
being present. He will not be present in the USERON.BBS
file but will be fully present in the SabreChat! session
as an individual node. SabreChat! should be called with
a node number higher than the highest number on the
board (i.e. node 4 on a 3 node system.). Preferably the
next node number to prevent large .USR files (i.e. don't
use node 49 :) unless you have plenty of space)
&<first_last name>
Default: Disabled
Example: SCHAT! &Shawn_Gresham N3
-- Shawn Gresham on imaginary node 3.
Example: SCHAT! &Gina_Lewter N3 B1200
-- Online User at 1200 baud on imaginary
node 3.
U s i n g S a b r e C h a t !
───────────────────────────────
Once in SabreChat! the user can activate commands by either
hitting control-[key] or by typing '/[key]' on a blank line.
The following commands are availiable to users once in
SabreChat!:
A Toggle ASCII/ANSI/Avatar mode.
This will toggle the code form that SabreChat! will
send color information to the remote user (if any).
Does not affect the local screen.
C Toggle 80/40 column wrapping.
This command toggle controls the point at which
SabreChat! performs its word wrapping.
(unfortunately affects local side too)
E Smile. (COURTESY COMMAND)
The user smiles.
F Change Conference.
This command displays a list of conferences and
allows the user to change which conference he is in.
Conference names are limited to normal ASCII
character and if the name is preceded with a '/'
then the conference is considered private and the
name will not show on the conference list, instead
PRIVATE is displayed. Only users knowing the name
may enter the conference.
G Check Online Messages.
This command tells SabreChat! to look for messages
sent by RA's page_online command and display them.
L Laugh. (COURTESY COMMAND)
The user laughs.
N Toggle Color Intensity.
This toggles between intense and normal colors in
ANSI and Avatar modes.
O List Users Currently Online.
This command lists the users curretly online in RA
as per USERON.BBS. It does not show hidden users
and will display the users handles instead of their
names if the H1 parameter is used on the command
line.
P Page Online.
This command is the same as RA's page_online option.
T Toggle Prompting Mode.
This allows the user to toggle thru all the prompting
modes availiable in SabreChat! (none,full name, intial)
W Wrist Watch.
Displays the time and the time remaining for the user.
X Exit SabreChat! and return to BBS.
Z Display the Help Screen.
Also some other keys have been added for the / commands.
/? and /h display the help screen.
/s smiles.
/q quits.
U s i n g S a b r e C h a t ! W i t h R A B B S
─────────────────────────────────────────────────────
SabreChat! has been designed on, around, and for Remote
Access Bulletin Boards. All of the command line parameters
have a RABBS counterpart to allow easy setup. A full listing
of these options are in the RA.DOC file. The most used
options are included below.
*G Ansi Graphics 0=off, 1=ansi, 2=avatar, 3=ansi/avatar
used with SChat!'s A option as A*G
*N Current Node
used with SChat!'s N option as N*N
*P Communications Port
used with SChat!'s P option as P*P
*T Time remaining in minutes
used with SChat!'s T option as T*T
These commands are the exact counterpart to SabreChat!'s
command line options. SabreChat! can be executed by
RA's Type 7 menu. Example as follows:
USER TEXT : (S)abre Chat!
MENU TYPE : 7
OTHER TEXT : SCHAT!.EXE N*N P*P T*T A*G
HOT KEY : 'S'
Currently, LANA settings for the net option will have to
be 'hard-set' at the command line because RA does not
have a counterpart.
OTHER TEXT : SCHAT!.EXE N*N P*P T*T A*G L0
U s i n g A M u l t i T a s k e r
─────────────────────────────────────
SabreChat! operates under a multitasker using the V <memory
buffers> option. To use SChat! with the V option, you must
first execute MXR!.COM before entering the multitasker (such
as DV.COM). This program creates the TSR's and buffers that
SabreChat! will use later to communicate inbetween windows.
Details about MXR!.COM and it's installation are described in
MXR!.DOC included in this archive. So far, SChat! has been
tested under DESQview and WINDOWS, but should work under any
multitasking environment using the V command line option.
You may have difficulty using SabreChat!'s direct screen
updating with a multitasker. Switching to the BIOS output
mode should help prevent confusing local displays and still
retain the status line. If problems persist move down to the
ASCII/ANSI text output and SabreChat! will operate as it has
in previous versions. A useful trick is to set the Z<screen
lines> option to the size of your windows (if any) so that you
can locally see the status bars for each node without the
windows scrolling.
Example of a DESQview call would be as follows:
SCHAT!.EXE N*N P*P A*G V
or
SCHAT!.EXE N*N P*P A*G S2 Z10 V (bios screen update half
screen size)
U s i n g N e t W o r k s
───────────────────────────
SabreChat! Version 2.05 was the first of the SCHAT! series
to allow communication via NetBios. Version 3.60 included
the excluded novell network users into the ballgame. Netbios
(L) and Novell (I) modes operate identically. A Group Name is
created by each node when SabreChat! is executed and text is
sent to and from that name.
Sometimes heavy drive access can cause character loss on
multi-server systems or on the server machine. If this
becomes a persisant and serious problem, try turning on the
DoubleChecking feature (command line option D) and this
should help cut down on losses.
C o n f e r e n c i n g
───────────────────────
With the introduction of version 4.07, SabreChat! now allows
conferencing with multitaskers as well as networks. The
following paragraphs have been written to help explain
SabreChat!'s conferencing abilities.
Conferences are like rooms set aside for users to talk to
each other in (in fact, you may wish to use conference names
that further this idea to help your users with the concept).
Users can create rooms by using the Control-F (/F) and
entering a room that is not on the list. Rooms disappear
after the last users leaves them. Users initially enter the
SCHAT! conference unless the SysOp specifies another with
the O command line option or the users are prompted for a
conference name by means of the U command line option.
Conference names beginning with '/' are considered private
and are listed so with the Control-F command. Only users
knowing the name may enter the conference since it is not
listed anywhere.
I have include a standard RA menu example to show what I mean.
SCHAT.ASC example
Welcome Traveller to the Towne of GreySmauk!
──────────────────────
(D)ragon Inn
(M)aid's Corner
(S)tory Teller's Block
(W)izard's Guild
(T)alk in Private
(A)rch-Mage's ONLY
(R)eturn to the Wilderness.
Select F,L,P,S or Q:
SCHAT.MNU examples for a network system:
'D' - Type 7 : SCHAT!.EXE ODRAGON-INN
'M' - Type 7 : SCHAT!.EXE OMAIDS-CORNER
'S' - Type 7 : SCHAT!.EXE OSTORY-TELLER
'W' - Type 7 : SCHAT!.EXE OMAGES-GUILD
'T' - Type 7 : SCHAT!.EXE U
'A' - Type 7 : SCHAT!.EXE O\ARCH-MAGE
'Q' - typical goto or return to menu depending on how
you have it setup.
The previous example is a simplified RA menu that shows all
the various options availiable for conferencing systems.
Option 'D' is an example of the sysop-defined group name
using 'DRAGON-INN' as the tag to communicate across the net.
The 'T' option allows two users to use a previously decided
number to conduct a private SChat! session or just to create
their own place using the U <user-defined group name>
option. And finally the 'A' menu option shows that mixed
with RA's restricted security access you could open
restricted access SChat! session with, in this case,
'ARCH-MAGE' as the group name.
I m m e d i a t e U s e r s
─────────────────────────────
Immediate User Mode allows you to use SabreChat! without the
need of a specific BBS or a BBS at all. This allows you to
specify the information normally passed by USERON.BBS. Making
it possible to use SabreChat! on the spur of the moment or
even on a network in the office to talk to someone else on the
net. Immediate User Mode releases SabreChat! from bulletin
board systems expanding it uses.
Two people or more people could talk across a NETBIOS or NOVELL
network by using a call similar to this:
User 1: SCHAT! N1 &Shawn_Gresham
User 2: SCHAT! N2 &Gina_Lewter
SabreChat! can be used in immediate mode with an online user just
by adding the port and baudrate
User 3: SCHAT! N3 &Joel_Karr B9600 P0
This feature allows other non-specific BBS's to use SabreChat! and
it also allows the sysop or a local user to pop into SabreChat! as
an imaginary node.
T e c h n i c a l i t i e s
───────────────────────────
For the sake of debugging, I have included a list of
system specific items that might cause conflict with
other software.
■ SChat! calls MXR! via interrupt 66h.
■ SChat! calls the fossil driver via interrupt 14h.
■ SChat! calls NetBios via interrupt 5ch.
■ SChat! uses the IPX low-level datagrams packets
in the Novell Netware (I) mode.
■ SChat! gets it's user information from USERON.BBS.
■ SChat! gets it's keyboard input from the fossil and
likewise uses it's screen output routines in text mode.
■ SChat! performs its Bios Output mode via interrupt 10h.
T h e F u t u r e
───────────────────
Here is a list of suggestions and various ideas that we have
spawned or have received from contributing users during the
development of SabreChat!. Whether these ideas become code
is dependent on the usefulness and difficulty of the task.
■ Split windows for ANSI users.
■ Log Entries.
■ A SysOp Capture Option for recording those unforgettable
moments.
If you have a nifty idea for an useful option, please drop us
some mail. After all... we can't think of everything. :)
Which leads to...
H e l p o r C o m m e n t s
───────────────────────────────
If you have any difficulties or comments, we would appreciate
any feedback (is there anybody out there?!?). Please call
Electrodes BBS (903) 868-2794 or NetMail at 1/19:55 to Shawn
Gresham or Joel Karr (SysOp). We are also available on the
RA_SUPPORT and RA_UTIL echos.
T h a n k s
───────────
I'd like to thank the following people for all the various
things they did in the development of SabreChat!.
Joel Karr, my number one ALPHA tester, for submitting his
delicate BBS for testing (still got your finger over that
reset button???) and for the invaluable programming help and
insight!
Les Harding, for all those hours of testing the "other side"
and the technical help that made programming easier.
Debbie Karr, for the moral support and soft drinks!!
And to all the users of Electrodes BBS who had to deal with
SabreChat!'s moody tendencies...thanks guys and gals!!!
You're the ones that I writing it for!
B e t a T e a m
────────────────
This beta cycle had to be contained within RA beta sites
only. I know there were others that had helped in testing
this version, but sorry guys, I didn't have your names!
Thanks to all the RA beta folks that gave a helping hand
with this release!!!
And to our old beta team, thanks guys! We will continue
beta testing thru you when possible. Starting with this
release we hope to get back to beta testing with you. We
have not forgotten you!!
A special thanks goes out to our fantastic Beta Team.
Let's all take our hats off for these few brave souls.
Keep up the good work gang.
Fred Horner Rod Hancock
The Private EaR Motor City Software
Waco, Tx Oshawa ON
1:388/10 1:229/418
(817) 776-9877 (416) 579-6318
Terry Harvey Bruce Bodger
Eagle One BBS The Truckstop BBS
Burwood NSW Australia Tulsa, OK
3:712/704 1:170/400
61-2-745-3190 (918) 254-6618
Documentation by Shawn Gresham and Joel Karr, 1991.
Good Bye!